Device auto pairing without touch and tap

ABSTRACT

A device-to-device (D2D) pairing assembly comprises: a first and a second device detecting and communicating (DDC) component communicatively coupled to each other and to a microprocessor that executes a device pairing parameter exchange (DPPE) utility, which configures the D2D pairing assembly to: detect a communicative coupling of a first user device to the first DDC component; receive from the first user device at least one first pairing parameter, which first pairing parameter enables another device to connect to and participate in a pairing session with the first user device; detect a communicative coupling of a second user device to the second DDC component; and communicate the at least one first pairing parameter to the second user device, via the second DDC component, to trigger the second user device to connect to and participate in a pairing session with the first user device via a direct device-to-device communication channel.

BACKGROUND

1. Technical Field

The present disclosure generally relates to pairing of user devices andin particular to a mechanism and improved method for pairing of two userdevices.

2. Description of the Related Art

Personal electronic devices or user devices, such as smart phones,tablets, and others are widely utilized for generating, storing, and/orcommunicating data and other content. A large number of these devicesinclude the capability, via use of a pairing mechanism and pairingutility, to communicatively connect the user device to a second deviceand exchange content. Content on the first device can then be sharedwith the second device via a pairing scheme involving the two devicesbeing placed in proximity to each other and communicating over a pairingor communication channel using short-range communication technology,such as near field communication (NFC), or Bluetooth®, or infrared (IR).Conventionally, the pairing of two user devices can require an exchangeof one or more pairing parameters, such as device authenticationcredentials, before each of the user devices is able to access the otherdevice and receive the content from the other device. Additionally, theestablishment of the pairing channel requires a series of user inputsand/or interactions with the devices to first enter into a pairing modeand then to establish the pairing channel. This setup of the devices forpairing can be time consuming and/or cumbersome, even with theavailability of the touch and tap connection methodology available withsome of the more sophisticated user devices.

BRIEF DESCRIPTION OF THE DRAWINGS

The disclosure will best be understood by reference to the followingdetailed description of illustrative embodiments when read inconjunction with the accompanying drawings, wherein:

FIG. 1 provides a block diagram representation of an exampledevice-to-device (D2D) pairing assembly with communicatively connecteddevice detection and communication (DDC) areas for receiving andcommunicating with respective user devices, according to one embodiment;

FIG. 2 is a block diagram representation of components utilized toenable the content transfer aspects of a D2D pairing assembly when afirst user device and a second user device are placed on, or inproximity to, a respective DDC area, according to one or moreembodiments;

FIG. 3 is a block diagram illustration of a first user device configuredwith enhanced pairing functionality to support device pairing via theD2D pairing assembly, in accordance with one embodiment;

FIG. 4 is a block sequence diagram showing directional flow ofcommunication signals between the first and second user devices andcomponents of the D2D assembly to establish a pairing channel betweenthe user devices, according to one or more embodiments; and

FIG. 5 is a flow chart of a method for completing D2D pairing of userdevices utilizing the D2D pairing assembly of FIGS. 1 and 2, accordingto one or more embodiments.

DETAILED DESCRIPTION

The illustrative embodiments of the present disclosure provide a methodand a device-to-device (D2D) pairing assembly for facilitating pairingof a first user device with a second user device. The D2D pairingassembly comprises: a first device detecting and communicating (DDC)area having corresponding first DDC components; a second DDC area havingcorresponding second DDC components communicatively coupled to the firstDDC components; and a microprocessor communicatively coupled to thefirst DDC component and to the second DDC component. A device pairingparameter exchange (DPPE) utility configures the D2D pairing assemblyto: detect a communicative coupling of a first user device to the firstDDC component; in response to detecting the communicative coupling ofthe first user device, receive from the first user device at least onefirst pairing parameter provided by a pairing application executing onthe first user device, which first pairing parameter enables anotherdevice to connect to and participate in a pairing session with the firstuser device; detect a communicative coupling of a second user device tothe second DDC component; and communicate the at least one first pairingparameter to the second user device, via the second DDC component, totrigger the second user device to connect to and participate in apairing session with the first user device via a direct device-to-devicepairing communication channel.

In one embodiment, the D2D pairing assembly detects either (i) aphysical placement of the first user device on the first DDC area or(ii) detects the first user device coming into proximity of and/orwithin communication range of the first DDC area. Similarly, the D2Dpairing assembly detects either a physical placement of the second userdevice on the second DDC area or detects the second user device cominginto proximity of and/or within communication range of the second DDCarea.

In the following detailed description of exemplary embodiments of thedisclosure, specific exemplary embodiments in which the various aspectsof the disclosure may be practiced are described in sufficient detail toenable those skilled in the art to practice the invention, and it is tobe understood that other embodiments may be utilized and that logical,architectural, programmatic, mechanical, electrical and other changesmay be made without departing from the spirit or scope of the presentdisclosure. The following detailed description is, therefore, not to betaken in a limiting sense, and the scope of the present disclosure isdefined by the appended claims and equivalents thereof.

Within the descriptions of the different views of the figures, similarelements are provided similar names and reference numerals as those ofthe previous figure(s). The specific numerals assigned to the elementsare provided solely to aid in the description and are not meant to implyany limitations (structural or functional or otherwise) on the describedembodiment. It will be appreciated that for simplicity and clarity ofillustration, elements illustrated in the figures have not necessarilybeen drawn to scale. For example, the dimensions of some of the elementsare exaggerated relative to other elements.

It is understood that the use of specific component, device and/orparameter names, such as those of the executing utility, logic, and/orfirmware described herein, are for example only and not meant to implyany limitations on the described embodiments. The embodiments may thusbe described with different nomenclature and/or terminology utilized todescribe the components, devices, parameters, methods and/or functionsherein, without limitation. References to any specific protocol orproprietary name in describing one or more elements, features orconcepts of the embodiments are provided solely as examples of oneimplementation, and such references do not limit the extension of theclaimed embodiments to embodiments in which different element, feature,protocol, or concept names are utilized. Thus, each term utilized hereinis to be given its broadest interpretation given the context in whichthat terms is utilized.

As further described below, implementation of the functional features ofthe disclosure described herein is provided within processing devicesand/or structures and can involve use of a combination of hardware,firmware, as well as several software-level constructs (e.g., programcode and/or program instructions and/or pseudo-code) that execute toprovide a specific utility for the device or a specific functionallogic. The presented figures illustrate both hardware components andsoftware and/or logic components.

Those of ordinary skill in the art will appreciate that the hardwarecomponents and basic configurations depicted in the figures may vary.The illustrative components are not intended to be exhaustive, butrather are representative to highlight essential components that areutilized to implement aspects of the described embodiments. For example,other devices/components may be used in addition to or in place of thehardware and/or firmware depicted. The depicted example is not meant toimply architectural or other limitations with respect to the presentlydescribed embodiments and/or the general invention.

The description of the illustrative embodiments can be read inconjunction with the accompanying figures. It will be appreciated thatfor simplicity and clarity of illustration, elements illustrated in thefigures have not necessarily been drawn to scale. For example, thedimensions of some of the elements are exaggerated relative to otherelements. Embodiments incorporating teachings of the present disclosureare shown and described with respect to the figures presented herein.

Referring now to FIG. 1, there is illustrated a device-to-device (D2D)pairing assembly 100 comprising: a first device detecting andcommunicating (DDC) area 105, also referenced as host device pad 105,and a second DDC area 125, also referenced as client device pad 125. Useof the terminology host device pad 105 and client device pad 125identifies a specific embodiment in which first DDC area 105 isallocated for receiving the user device that will be utilized as thehost device within a pairing scheme, while second DDC is allocated forreceiving the second user device that will be the client device withinthe pairing scheme. For consistency, the device that is placed orbrought into proximity with first DDC area 105 is referred to as thefirst user device, represented as first user device 150. The first andsecond DDC areas 105 and 125 can, in one or more implementations,represent areas delineated on the D2D pairing assembly 100 for (a)direct physical placement of a first user device 150 and a second userdevice 170 or (b) close proximity placement of the first user device 150and the second user device 170, respectively, within communication rangeof the corresponding transceivers (see FIG. 2).

As shown, located within first DDC area 105 is a corresponding first DDCcomponent 107, which includes or comprises a short-range communicationcomponent or tag 120. Similarly, located within second DDC area 125 is acorresponding second DDC component 127, which includes or comprisesanother short-range communication component or tag 130. As shown, firstand second DDC components 107 and 127 are both configured with one ormore wireless communication mechanisms, respectively illustrated as nearfield communication (NFC)/radio frequency identification(RFID)/Bluetooth (BT) tags 120 and 130. The first and second DDCcomponents 107 and 127 enable the D2D pairing assembly 100 tocommunicatively connect with the user devices 150 and/or 170,respectively, via a short-range wireless communication 122, 132.

As further illustrated, D2D pairing assembly 100 can include amicroprocessor 110 and one or more storage devices, represented bymemory 115. According to one embodiment, microprocessor 110 and memory115 can generally exist externally to first and second DDC areas 105 and125 and operate as components of D2D pairing assembly 100. With thisembodiment, microprocessor 110 is communicatively coupled to the firstDDC component 107 and to the second DDC component 127. Each of first DDCcomponent 107 and second DDC component 127 includes one or moremechanisms for communicating between the two components 107 and 127. Asshown, the second DDC component 127 is communicatively coupled to thefirst DDC component 107 via one of a wired cable connector 140 or awireless medium 145 using one of the available close-range wirelesscommunication protocols and supporting devices. It is appreciated thatthere is no specific requirement of a space separation between first DDCcomponent 107 and second DDC component 127. The two DDC components 107and 127 can be adjacent to each other, positioned in a verticalalignment (top-and-bottom or back-to-back) or in other positionsrelative to each other within the D2D pairing assembly 100.

Referring now to FIG. 2, there is provided an in-use view presenting amore detailed representation of D2D pairing assembly 100 with the twouser devices, first user device 150 and second user device 170, eachplaced physically on top of first DDC area 105 and second DDC area 125,respectively, and engaging in communication exchange via D2D pairingassembly 100. Unlike in FIG. 1 where the user devices 150 and 170 areshown physically displaced from the first and second DDC areas 105 and125, each user device 150 and 170 of FIG. 2 is physically placed atop arespective DDC area 105 and 125. By extension, the user devices 150 and170 are also in close proximity to respective first DDC components 107and 127. In at least one embodiment, the physical contact of at leastthe first user device 150 with the corresponding first DDC component 105triggers the various pairing setup functions described herein. Inalternate embodiments, the physical contact of both first user device150 and second user device 170 with respective first DDC component 105and second DDC component 125 (as represented by FIG. 2) is required totrigger the pairing setup functions. In one embodiment, the location ofthe DDC components 107 and 127 within the DDC areas 105 and 125 arepre-determined to provide unobstructed communication with thetransceiver components of the user devices that are placed atop the DDCareas 105 and 125.

As further shown by FIG. 2, D2D pairing assembly 100 comprises: anunderlying pad 200 that identifies a perimeter and a surface of the D2Dpairing assembly 100; a first DDC area 105 on which the first userdevice can be placed; and a second DDC area 125 on which the second userdevice can be placed. D2D pairing assembly 100 also comprises functionalelectronic circuitry associated with the first and second DDC components107 and 127, which enable at least one of a wireless signalcommunication (145) between the first DDC component 107 and the secondDDC component 127 and direct communication via a communication bus 140extending between the first DDC component 107 and the second DDCcomponent 125. Several of the additional, internal functional componentsof D2D pairing assembly 100 are illustrated at the bottom section ofFIG. 2. These functional electronic circuitry components are illustratedin communication with each other, as with an example in-use case, withcommunication lines presented by directional arrows. Dashed arrowsindicate optional and/or alternate communications that can occur in someembodiments, but excluded in others.

According to the illustrated embodiment, the electronic circuitrycomprises: a first DDC data transmitter 255 that transmits pairingparameters (215) received from the first user device 150; and a secondDDC data receiver 270 for receiving the pairing parameters (215) beingtransmitted from the first device pad 105. In one or more embodiments,the first DDC data transmitter 255 is a component of a first DDC datatransceiver 257 and the second DDC data receiver 270 is a component of asecond DDC data transceiver 277. The transceivers 257, 277 enablebi-directional transfer of pairing information between a first userdevice and a second user device communicatively coupled to respectiveones of the first DDC component 105 and the second DDC component 125.

Accordingly, in one or more embodiments, the first DDC component 107comprises a first data receiver and a first data transmitter, whichrespectively receives the pairing parameters and transmits the receivedpairing parameters to the second DDC component 127. Further, the secondDDC component 127 comprises a second data receiver that receives thepairing parameters from the first DDC component 107 and a second datatransmitter that transmits the pairing parameters to the second userdevice 170 from the second DDC component 127.

In the various embodiments, the first data receiver can be one of aradio frequency identifier (RFID) receiver and a near fieldcommunication (NFC) receiver. Similarly, the second data transmitter canbe one of a radio frequency identifier (RFID) transmitter and a nearfield communication (NFC) transmitter.

FIG. 2 illustrates a different configuration of microprocessor 110 andmemory 115 introduced in FIG. 1. With this configuration, memory 115 isdepicted as an on-chip memory with microprocessor 110. To support andtrigger or enable the functions described herein, microprocessor 110 isconfigured with a device pairing parameter exchange (DPPE) utility 260that executes on the microprocessor 110 and configures the D2D pairingassembly 100 to perform a series of functions to assist in pairing oftwo or more user devices, such as first user device 150 and second userdevice 170. According to one embodiment, DPPE utility 260 can be storedwithin memory 115 and accessed for execution on microprocessor 110 whenrequired, e.g., when microprocessor 110 is triggered to perform thedevice pairing configuration processes.

According to one or more embodiments, DPPE utility 260 configures theD2D pairing assembly 100 to detect a communicative coupling of a firstuser device 150 to the first DDC component 107; and in response todetecting the communicative coupling of the first user device 150,receive from the first user device 150 at least one first pairingparameter (e.g., user device ID 215) provided by a pairing application210 executing on the first user device 150. The provided first pairingparameter enables another device to connect to and participate in apairing session with the first user device 150. The DPPR utility 260further configures the D2D pairing assembly 100 to detect acommunicative coupling of a second user device 170 to the second DDCcomponent 127; and communicate the at least one first pairing parameterto the second user device 170, via the second DDC component 127, totrigger the second user device 170 to connect to and participate in apairing session with the first user device 150 via a directdevice-to-device communication medium (see 410, FIG. 4).

It is appreciated that the reference to at least one first pairingparameter is indicative of the fact that a single pairing parameter canbe communicated, in some embodiments, while multiple pairing parameterscan be communicated in other embodiments. The actual pairing parameter/scan be ones that are pre-programmed for automatic transmission onreceipt at the user device of a signal indicating that the user deviceis in communication with a DDC component of a D2D pairing assembly.

According to one embodiment, the DPPE utility 260 further configures theD2D pairing assembly 100 to: in response to detecting the communicativecoupling of the second user device 170, receive from the second userdevice 170 at least one second pairing parameter associated with thesecond user device 170, and which uniquely identifies a second userdevice; and communicate the at least one second pairing parameter to thefirst user device 150 to enable the first user device 150 to participatein the pairing session with the second user device 170.

In one or more of the described embodiments, the DPPE utility 260further configures the device-to-device pairing assembly 100 to: inresponse to completion of a transfer of the at least one first pairingparameter to the second device 170 via the D2D pairing assembly 100, (i)de-couple and/or suspend communication between the first user device 150and the first DDC component 107 and (ii) de-couple or terminatecommunication between the second user device 170 and the second DDCcomponent 127. Thus, any subsequent communication and/or contenttransfer between the first user device 150 and the second user device170, occurs via the pairing session, and is completed independent of theD2D pairing assembly 100.

When the first pairing of the second user device 170 to the first userdevice 150 is completed, subsequent pairings of other devices with thefirst user device 150 can be completed. Thus, as one example, the DPPEutility 260 further configures the device-to-device pairing assembly 100to: detect a communicative coupling of a third user device with thesecond DDC component 127 while the first user device is paired to thesecond user device 170 and is still communicatively coupled to the firstDDC component; and in response to detecting the third user devicecommunicatively coupled to the second DDC component 127 while the firstuser device 150 is still communicatively coupled with the first DDCcomponent 107, communicate a set of pairing parameters received from thefirst user device 150 to the third user device to enable the third userdevice to complete device-to-device pairing with the first user device150. When the pairing of the third device is being established while thefirst user device 150 and second user device 170 are still paired, theset of pairing parameters provided to the third user device aredifferent pairing parameters than being utilized to complete or conductthe device-to-device pairing of the first user device 150 and seconduser device 170.

In one or more embodiments, an alternate method of differentiating thetwo pairings of different devices from each other involves the firstuser device 150 completing different encoding of the pairing parameterssuch that each set of pairing parameters provided for each differentpairing are differently encoded. Accordingly, the DPPE utility 260further configures the D2D pairing assembly 100 to: detect acommunicative coupling of a third user device to the second DDCcomponent while the first user device 150 is paired to the second userdevice 170 and is still communicatively coupled to the first DDCcomponent 107; and in response to detecting the third user devicecommunicatively coupled to the second DDC component 127 while the firstuser device 150 is paired to the second user device 170 and stillcommunicatively coupled to the first DDC component 107, communicate adifferently-encoded version of the at least one first pairing parameterthat is received from the first user device 150 to the third user deviceto enable the third user device to complete device-to-device pairingwith the first user device 150 using differently-encoded pairingparameters than being utilized to complete the device-to-device pairingof the first user device 150 and second user device 170.

In one embodiment, the pairing functionality and/or pairingconfiguration of the user devices can be enhanced to support thefeatures described herein. As illustrated in FIGS. 1 and 2, each userdevice 150 and 170 can include a display 155/175 and a pairing userinterface 160/180 that can be opened on display 155/175 during pairingsetup and subsequent content exchange. However, it is appreciated thatother configurations of user devices can be utilized within thedisclosed concepts, including user devices that do not have a displayand/or a pairing user interface. In FIG. 2, in addition to theseexternally visible pairing user interfaces 160/180, first user device150 also includes a pairing application 210, which includes a first userdevice identifier (ID) 215 and a pairing configuration setup andnotification utility 220 which enables a user of first user device 150to configure first user device 150 for pairing with another user device.Second user device 170 can be similarly configured as first user device150 or differently configured. As further shown in FIG. 2, second userdevice 170 includes a pairing established notification message 230 thatcan be presented on display 175 or presented as an audible notification,in alternate embodiments.

Referring to FIG. 3, there is presented a block diagram illustration ofan example first user device 150 including functional componentsrequired to complete device pairing, in accordance with one embodiment.According to the illustration, first user device (UD1) 150 is acommunication device that is designed to communicate with other devicesvia one of a wireless communication network, represented by base station338 (evolution node B, eNodeB) and antenna 336, and short-rangecommunication components for supporting one or more pairingtechnologies, e.g., Bluetooth® transceiver 366 and near fieldcommunication (NFC) transceiver 368, among others. UD1 150 can be one ofa host of different types of devices, including but not limited to, amobile cellular phone or smart-phone, a laptop, a net-book, anultra-book, and/or a tablet computing device. These various devices allprovide and/or include the necessary hardware and software to enablepairing of UD1 with a second UD (UD2) 170 or third UD (UD3) 345,included various functions associated with establishing and supportingthe pairing connection. Additionally, UD1 150 includes the hardware andsoftware or firmware to support the various wireless or wiredcommunication functions.

Referring now to the component makeup and the associated functionalityof the presented components, UD1 150 comprises processor integratedcircuit (IC) 302, which connects via a plurality of bus interconnects(illustrated by the bi-directional arrows) to a plurality of functionalcomponents of UD1 150. Processor IC 302 can include one or moreprogrammable microprocessors, such as a data processor 304 and a digitalsignal processor (DSP) 306, which may both be integrated into a singleprocessing device, in some embodiments. The processor IC 302 controlsthe communication, image capture, and other functions and/or operationsof UD1 150. These functions and/or operations thus include, but are notlimited to, application data processing and signal processing.

Connected to processor IC 302 is memory 308, which can include volatilememory and/or non-volatile memory. One or more executable applicationscan be stored within memory for execution by data processor 304 onprocessor IC 302. For example, memory 308 is illustrated as containingpairing application 210, which includes pairing setup utility 312,pairing notification module 314, and pairing parameter encoding utility316. The associated functionality and/or usage of each of the softwaremodules are generally known, except that the modules can be enhanced tosupport establishment of a pairing channel that is set up using the D2Dpairing assembly and associated functionality described by the presentdisclosure. It is also appreciated that the various software modules canbe independent modules that communicate with each other via processorexecution of respective program code.

Also shown coupled to processor IC 302 is storage 350 which can be anytype of available storage device capable of storing one or moreapplication software and data. It is further appreciated that in one ormore alternate embodiments, the device storage can actually be remotestorage and not an integral part of the device itself. As provided,storage 350 contains pairing parameters 215 and shareable data orcontent 357. The specific usage and/or functionality associated withthese components are described in greater detail in the followingdescriptions.

According to one aspect, pairing setup utility 312 of both UD1 150 andUD2 170 is an enhanced or a modified pairing setup module that enablesthe functionality of automatically transmitting the at least one firstpairing parameter and the at least one second pairing parameter inresponse to detection of a connection with DDC component 107/127 of aD2D pairing assembly. In one embodiment, DDC component 107/127 transmitsa request for return of pairing parameters in response to the detectionof the user device establishing a communication with the DDC component107/127. As one aspect of the disclosure, the paring parameters 215requested or received from user devices communicatively coupled to thefirst DDC component 107 can be different from the pairing parameters (ifany) requested and/or received from user devices communicatively coupledto the second DDC component 127. Depending on implementation and/orspecific design of D2D assembly or configuration of pairing setuputility 312, the pairing parameters 215 can include one of more of:device authentication credentials, pairing channel information, pairingprotocol selected from among the technology available and/or supportedon the user device, and/or other parameters. It is appreciated that thetransmitted paring parameters 215, while described as being at least oneor a set of parameters can in the simplest implementation be a singlepairing parameter that establishes or identifies the pairing channel orthe pairing technology for use in completing the device pairing.

UD1 150 can also comprise a plurality of input/output (I/O) devices,including one or more input devices 320 and/or one or more outputdevices 325, such as display 155. UD1 150 can also include a subscriberinformation module (SIM) 322 which can provide unique identificationinformation of the subscriber that owns or utilizes UD1 150, as well asspecific contacts and device settings associated with the particularsubscriber.

According to one aspect of the disclosure and as illustrated by FIG. 3,UD1 150 supports at least one and potentially many forms of wireless,over-the-air communication, which allows UD1 150 to transmit and receivecommunication with at least one second device. As a device supportingwireless communication, UD1 150 can be one of, a mobile device acordless telephone, and a computing device, such as a laptop, tablet,smart phone, personal digital assistant, or other processing devicesconnected to a wireless modem, to name a few. To support the wirelesscommunication, UD1 150 includes one or more communication components,including wireless transceiver 330 with connected antenna 332, wirelessLAN module 362, RFID 364, Infrared 365, Bluetooth® transceiver 366, andnear field communication transceiver module 368. Collectively, thesewireless components provide a communication mechanism 360 by which UD1150 can communicate with other devices and networks. For purposes of thefollowing illustrations and associated descriptions thereof, one pairingcommunication mode is assumed to be NFC, supported by NFC transceivermodule 368, while another pairing communication mode is assumed to beBluetooth®, supported by Bluetooth® transceiver 366.

The wireless communication can be via a standard wireless network, whichincludes a network of base stations, illustrated by evolution Node B(eNodeB) 338 and associated base station antenna 336. A firstover-the-air signal 334 is illustrated interconnecting base stationantenna 336 with local antenna 332 of UD1 150. Additionally,communication with the at least one second device (UD2) 170 can beestablished via near field communication transceiver module 368. In atleast one embodiment, UD1 150 can establish a pairing channel with andexchange communication with one or more second devices, of which UD2 170and UD3 345 are illustrated. As described in further detail below, eachof UD2 170 and UD3 345 can be second devices with which UD1 150 canestablish a pairing communication channel, using over-the-air signaltransmission, following the exchange of specific authentication and/oraccess credentials. In one embodiment, a single pairing channel can beestablished with each different short-range communication protocol, andmultiple different channels can be established concurrently withmultiple second and third devices using the available protocols. Thus,UD2 170 can be paired with UD1 150 using first pairing parameters toconnect over Bluetooth® (366), while UD3 345 can be paired with UD1 150using either different pairing parameters or a differently-encodedversion of the first pairing parameters to connect over NFC (368).

FIG. 4 is a block sequence diagram showing directional flow of signalconnectivity and/or data exchange between the various user devices andDDC components 107, 127 of D2D pairing assembly, introduced in thepreceding figures (FIGS. 1, 2, and 3), according to one or moreembodiments. Each communication signal path is labeled with anassociated letter A through E, indicating an initial order ofcommunication exchange. Thus, first DDC component 107 generates firstcommunication signal path A which communicatively connects first DDCcomponent 107 with UD1 150. First DDC component 107 requests and/orreceives the at least one first pairing parameter from UD1 150 viacommunication signal path A. Specifically, UD1 150 transmits the atleast one first pairing parameter to first DDC component 107 via theestablished communication channel (A). First DDC component 107 thentransfers the received pairing parameter/s via one of wirelesscommunication path, B1, or wired communication path, B2, to second DDCcomponent 127. Second DDC component 127 then transmits the receivedpairing parameters via communication path C to UD2 170. In at least oneembodiment, UD2 170 can also communicate information, such as the atleast one second pairing parameter, to second DDC component 127 viacommunication path C. This reverse communication path is illustrated asitalicized C within a dashed circle indicating that this communicationis an optional and/or alternate embodiment. Once the abovecommunications are completed over communication paths A, B, and C, andthe necessary pairing parameters have been communicated from UD1 150 toUD2 170 and, if necessary, from UD2 170 to UD1 150, communication path Cis disconnected and pairing communication channel (path D) 410 isestablished between UD1 150 and UD2 170. The wireless communicationpath, D, between UD1 150 and the second user device, UD2, 170 can beestablished via near field communication, Bluetooth, IR, or othershort-range communication technology. Notably, this wirelesscommunication channel (path D) can co-exist along with a networkcommunication path E, comprising over-the-air signals 420 extending fromUD1 150 to UD2 170 via wireless network (370, FIG. 3), using one or moreintermediary base station antennas. Notably, the establishment of thepairing communication occurs using the D2D pairing assembly to transferthe required pairing parameters between the devices being paired.

FIG. 5 is a flow chart of a method for completing D2D pairing utilizingthe pairing assembly of FIGS. 1 and 2, with two or more user devices,according to one or more embodiments. The method 500 facilitates pairingof a first user device with a second user device, via use of the D2Dpairing assembly. With the descriptions which follow, certain aspects ofthe methods can be implemented by microprocessor 110 executing programcode from DPPE utility 260. Generally, the method 500 can be describedas being performed by one or more of D2D pairing assembly 100,microprocessor 110 or execution of a specific utility, e.g., DPPEutility 260, without limitation. Also, method 500 is described withreference to components and features of the preceding figures, FIGS.1-4, which provide specific examples of the embodiments described by themethod.

As illustrated by FIG. 5, method 500 begins at block 502, which providesD2D pairing assembly 100 detecting a communicative coupling of a firstuser device 150 to the first DDC component 107. At block 504, inresponse to detecting the communicative coupling of the first userdevice 150, method 500 includes D2D pairing assembly 100 receiving fromthe first user device 150 at least one first pairing parameter providedby a pairing application executing on the first user device 150, whichfirst pairing parameter enables another device to connect to andparticipate in a pairing session with the first user device 150. Atdecision block 506, method 500 further provides D2D pairing assembly 100determining whether a communicative coupling of a second user device 170is detected to second DDC component 127. In response to detecting thecommunicative coupling of the second user device to the second DDCcomponent 127, method 500 provides: communicating the at least one firstpairing parameter to the second user device 170, via the second DDCcomponent 127, to trigger the second user device 170 to connect to andparticipate in a pairing session with the first user device 150 via adirect device-to-device communication medium (block 512).

According to one embodiment, the method 500 includes the D2D pairingassembly detecting one of (i) a physical placement of the first userdevice on the first DDC area and (ii) the first user device coming intoproximity of and/or within communication range of the first DDC area.Then, in response to the detecting, the method 500 further includestriggering the DDC component to establish a communication with the firstuser device via a short-range wireless communication protocol supportedby the first user device. Similarly detecting and triggering functionsare performed to establish the communication with the second userdevice, when the second DDC component detects the second user devicecoming into proximity of and/or within communication range of the secondDDC area.

In one or more alternate embodiments, and as illustrated by thedashed-line blocks, method 500 can include receiving from the seconduser device 170 at least one second pairing parameter associated withthe second user device 170, and which uniquely identifies the seconduser device (block 508); and communicating the at least one secondpairing parameter to the first user device 150 to enable the first userdevice 150 to participate in the pairing session with the second userdevice (block 510).

The pairing session that is established at block 512 involvescommunication via a pairing channel that is enabled using one of theavailable close-range communication mechanism and protocols, such asBluetooth, NFC, or IR, for example. And, once the pairing sessionparameters are exchanged via the D2D pairing assembly 100, the DPPEutility 260 causes the D2D pairing assembly 100 to disconnect at leastone of (a) the communicative coupling of the first DDC component withthe first user device 150 and (b) the communicative coupling of thesecond DDC component with the second user device 170. Specifically,within the process presented by method 500, and as shown at block 514,method 500 includes disconnecting or suspending at least thecommunicative coupling of the second DDC component with the second userdevice 170. The disconnection or suspension is triggered to occur inresponse to completion of a transfer of at least the first pairingparameter via the D2D pairing assembly. Following this disconnection,subsequent exchanges of communication, including information transferbetween the first user device and the second user device, occur via thepairing session, independent of the D2D pairing assembly. It isappreciated that the disconnection may be triggered in response to auser removing the first device and/or the second device away from withinthe communication range of the respective DDC component.

Following block 514, method 500 can optionally include detecting acommunicative coupling of a third user device to the second DDCcomponent while the first user device is paired to the second userdevice and still communicatively coupled to the first DDC component(block 516). Then, in response to detecting the third user devicecommunicatively coupled to the second DDC component while the first userdevice is paired to the second user device and still communicativelycoupled to the first DDC component, method 500 optionally includescommunicating a third pairing parameter received from the first userdevice to the third user device to enable the third user device tocomplete device-to-device pairing with the first user device usingdifferent pairing parameters than being utilized to complete thedevice-to-device pairing of the first user device and second user device(block 518). These optional processes are illustrated by dashed boxeswithin method 500. According to one or more embodiments, the thirdpairing parameter is an encoded copy of the first pairing parameter, andthe method 500 then includes communicating a differently-encoded versionof the first pairing parameter that is received from the first userdevice to the third user device to enable the third user device tocomplete device-to-device pairing with the first user device usingdifferently-encoded pairing parameters than being utilized to completethe device-to-device pairing of the first user device and second userdevice. Method 500 then ends.

In the flow chart presented herein, certain functions and/or processesof the methods can be combined, performed simultaneously or in adifferent order, or perhaps omitted, without deviating from the spiritand scope of the described innovation. While the method functions orprocesses are described and illustrated in a particular sequence, use ofa specific sequence of steps is not meant to imply any limitations onthe innovation. Changes may be made with regards to the sequence ofsteps without departing from the spirit or scope of the presentinnovation. Use of a particular sequence is therefore, not to be takenin a limiting sense, and the scope of the present innovation is definedonly by the appended claims.

As will be appreciated by one skilled in the art, embodiments of thepresent innovation may be embodied as a system, device, and/or method.Accordingly, embodiments of the present innovation may take the form ofan entirely hardware embodiment or an embodiment combining software andhardware embodiments that may all generally be referred to herein as a“circuit,” “module” or “system.”

Aspects of the present innovation are described below with reference toflowchart illustrations and/or block diagrams of methods, apparatus(systems) and computer program products according to embodiments of theinnovation. It will be understood that each block of the flowchartillustrations and/or block diagrams, and combinations of blocks in theflowchart illustrations and/or block diagrams, can be implemented bycomputer program instructions. These computer program instructions maybe provided to a processor of a general purpose computer, specialpurpose computer, or other programmable data processing apparatus toproduce a machine, such that the instructions, which execute via theprocessor of the computer or other programmable data processingapparatus, create means for implementing the functions/acts specified inthe flowchart and/or block diagram block or blocks.

While the innovation has been described with reference to exemplaryembodiments, it will be understood by those skilled in the art thatvarious changes may be made and equivalents may be substituted forelements thereof without departing from the scope of the innovation. Inaddition, many modifications may be made to adapt a particular system,device or component thereof to the teachings of the innovation withoutdeparting from the essential scope thereof. Therefore, it is intendedthat the innovation not be limited to the particular embodimentsdisclosed for carrying out this innovation, but that the innovation willinclude all embodiments falling within the scope of the appended claims.Moreover, the use of the terms first, second, etc. do not denote anyorder or importance, but rather the terms first, second, etc. are usedto distinguish one element from another.

The terminology used herein is for the purpose of describing particularembodiments only and is not intended to be limiting of the innovation.As used herein, the singular forms “a”, “an” and “the” are intended toinclude the plural forms as well, unless the context clearly indicatesotherwise. It will be further understood that the terms “comprises”and/or “comprising,” when used in this specification, specify thepresence of stated features, integers, steps, operations, elements,and/or components, but do not preclude the presence or addition of oneor more other features, integers, steps, operations, elements,components, and/or groups thereof.

The corresponding structures, materials, acts, and equivalents of allmeans or step plus function elements in the claims below are intended toinclude any structure, material, or act for performing the function incombination with other claimed elements as specifically claimed. Thedescription of the present innovation has been presented for purposes ofillustration and description, but is not intended to be exhaustive orlimited to the innovation in the form disclosed. Many modifications andvariations will be apparent to those of ordinary skill in the artwithout departing from the scope and spirit of the innovation. Theembodiment was chosen and described in order to best explain theprinciples of the innovation and the practical application, and toenable others of ordinary skill in the art to understand the innovationfor various embodiments with various modifications as are suited to theparticular use contemplated.

What is claimed is:
 1. A device-to-device (D2D) pairing assemblycomprising: a first device detecting and communicating (DDC) component;a second DDC component communicatively coupled to the first DDCcomponent; a microprocessor communicatively coupled to the first DDCcomponent and to the second DDC component and which is configured with adevice pairing parameter exchange (DPPE) utility that executes on themicroprocessor and configures the D2D pairing assembly to: detect acommunicative coupling of a first user device to the first DDCcomponent; in response to detecting the communicative coupling of thefirst user device, receive from the first user device at least one firstpairing parameter provided by a pairing application executing on thefirst user device, which at least one first pairing parameter enablesanother device to connect to and participate in a pairing session withthe first user device; detect a communicative coupling of a second userdevice to the second DDC component; and communicate the at least onefirst pairing parameter to the second user device, via the second DDCcomponent, to trigger the second user device to connect to andparticipate in the pairing session with the first user device via adirect device-to-device communication medium.
 2. The D2D pairingassembly of claim 1, wherein the DPPE utility further configures thedevice-to-device pairing assembly to: in response to detecting thecommunicative coupling of the second user device, receive from thesecond user device at least one second pairing parameter associated withthe second user device, and which uniquely identifies a specific seconduser device; and communicate the at least one second pairing parameterto the first user device to enable the first user device to participatein the pairing session with the specific second user device.
 3. The D2Dpairing assembly of claim 1, wherein the DPPE utility further configuresthe device-to-device pairing assembly to: in response to completion of atransfer of the at least one first pairing parameter via the D2D pairingassembly, de-couple communication between the first user device and thefirst DDC component and de-couple communication between the second userdevice and the second DDC component, wherein a subsequent exchange ofcommunication, including information transfer between the first userdevice and the second user device, occurring via the pairing session, iscompleted independent of the D2D pairing assembly.
 4. The D2D pairingassembly of claim 1, wherein the DPPE utility further configures thedevice-to-device pairing assembly to: detect a communicative coupling ofa third user device to the second DDC component while the first userdevice is paired to the second user device and still communicativelycoupled to the first DDC component; and in response to detecting thethird user device communicatively coupled to the second DDC componentwhile the first user device is paired to the second user device andstill communicatively coupled to the first DDC component, communicate atleast one different pairing parameter received from the first userdevice to the third user device to enable the third user device tocomplete device-to-device pairing with the first user device using atleast one different pairing parameter than being utilized to completethe device-to-device pairing of the first user device and second userdevice.
 5. The D2D pairing assembly of claim 1, wherein the DPPE utilityfurther configures the device-to-device pairing assembly to: detect acommunicative coupling of a third user device to the second DDCcomponent while the first user device is paired to the second userdevice and still communicatively coupled to the first DDC component; andin response to detecting the third user device communicatively coupledto the second DDC component while the first user device is paired to thesecond user device and still communicatively coupled to the first DDCcomponent, communicate a differently-encoded version of at least one ofthe at least one first pairing parameter that is received from the firstuser device to the third user device to enable the third user device tocomplete device-to-device pairing with the first user device using atleast one differently-encoded pairing parameter than being utilized tocomplete the device-to-device pairing of the first user device andsecond user device.
 6. The D2D pairing assembly of claim 1, furthercomprising: an underlying pad that identifies a perimeter of thedevice-to-device pairing assembly; a first device pad on which the firstuser device can be place; a second device pad on which the second userdevice can be placed; and electronic circuitry associated with the firstand second device pads which enable at least one of a wireless signalcommunication between the first device pad and the second device pad anddirect communication via a communication bus extending between the firstdevice pad and the second device pad.
 7. The D2D pairing assembly ofclaim 6, wherein the electronic circuitry comprises: a first DDC datatransmitter that transmits pairing parameters that are received from thefirst user device; and a second DDC data receiver for receiving pairingparameters transmitted from the first device pad.
 8. The D2D pairingassembly of claim 7, wherein the first DDC data transmitter is acomponent of a first DDC data transceiver and the second DDC datareceiver is a component of a second DDC data transceiver forbi-directional transfer of pairing information between a first userdevice and a second user device communicatively coupled to respectiveones of the first DDC component and the second DDC component.
 9. The D2Dpairing assembly of claim 1, wherein: the first DDC component comprisesa first data receiver and a first data transmitter, which respectivelyreceives the at least one first pairing parameter and transmits thereceived at least one first pairing parameter to the second DDCcomponent; and the second DDC component comprises a second data receiverthat receives the at least one first pairing parameter from the firstDDC component and a second data transmitter that transmits the at leastone first pairing parameter to the second user device from the secondDDC component.
 10. The D2D pairing assembly of claim 9, wherein: thefirst data receiver DDC is one of a radio frequency identifier (RFID)receiver and a near field communication (NFC) receiver; and the seconddata transmitter DDC is one of a radio frequency identifier (RFID)transmitter and a near field communication (NFC) transmitter.
 11. Amethod for facilitating pairing of a first user device with a seconduser device, the method comprising: detecting a communicative couplingof a first user device to a first device detecting and communicating(DDC) component; and in response to detecting the communicative couplingof the first user device, receiving from the first user device at leastone first pairing parameter provided by a pairing application executingon the first user device, which at least one first pairing parameterenables another device to connect to and participate in a pairingsession with the first user device; detecting a communicative couplingof a second user device to a second DDC component that iscommunicatively coupled to the first DDC component on a device-to-device(D2D) pairing assembly; and communicating the at least one first pairingparameter to the second user device, via the second DDC component, totrigger the second user device to connect to and participate in thepairing session with the first user device via a direct device-to-devicecommunication medium.
 12. The method of claim 11, further comprising: inresponse to detecting communicative coupling of the second user device:receiving from the second user device at least one second pairingparameter associated with the second user device, and which uniquelyidentifies a specific second user device; and communicating the at leastone second pairing parameter to the first user device to enable thefirst user device to participate in the pairing session with thespecific second user device.
 13. The method of claim 11, furthercomprising: in response to completion of a transfer of the at least onefirst pairing parameter via the D2D pairing assembly: disconnecting thecommunicative coupling of the first DDC component with the first userdevice; and disconnecting the communicative coupling of the second DDCcomponent with the second user device; wherein a subsequent exchange ofcommunication, including information transfer between the first userdevice and the second user device, occurring via the pairing session, iscompleted independent of the D2D pairing assembly.
 14. The method ofclaim 11, further comprising: detecting detect a communicative couplingof a third user device to the second DDC component while the first userdevice is paired to the second user device and still communicativelycoupled to the first DDC component; and in response to detecting thethird user device communicatively coupled to the second DDC componentwhile the first user device is paired to the second user device andstill communicatively coupled to the first DDC component, communicatingto the third user device at least one different pairing parameterreceived from the first user device to enable the third user device tocomplete device-to-device pairing with the first user device using atleast one different pairing parameter than being utilized to completethe device-to-device pairing of the first user device and second userdevice.
 15. The method of claim 11, further comprising: detecting acommunicative coupling of a third user device to the second DDCcomponent while the first user device is paired to the second userdevice and still communicatively coupled to the first DDC component; andin response to detecting the third user device communicatively coupledto the second DDC component while the first user device is paired to thesecond user device and still communicatively coupled to the first DDCcomponent, communicating a differently-encoded version of at least oneof the at least one first pairing parameter that is received from thefirst user device to the third user device to enable the third userdevice to complete device-to-device pairing with the first user deviceusing at least one differently-encoded pairing parameter than beingutilized to complete the device-to-device pairing of the first userdevice and second user device.
 16. The method of claim 11, wherein thedevice-to-device pairing assembly comprises: an underlying pad thatidentifies a perimeter of the device-to-device pairing assembly; a firstdevice pad on which the first user device can be place; a second devicepad on which the second user device can be placed; and electroniccircuitry associated with the first and second device pads which enablesat least one of a wireless signal communication between the first devicepad and the second device pad and direct communication via acommunication bus extending between the first device pad and the seconddevice pad.
 17. The method of claim 16, wherein the electronic circuitrycomprises: a first DDC data transmitter that transmits pairingparameters that are received from the first user device; and a secondDDC data receiver for receiving the pairing parameters transmitted fromthe first device pad.
 18. The method of claim 11, wherein the first DDCdata transmitter is a component of a first DDC data transceiver and thesecond DDC data receiver is a component of a second DDC data transceiverfor bi-directional transfer of pairing information between a first userdevice and a second user device communicatively coupled to respectiveones of the first DDC component and the second DDC component.
 19. Themethod of claim 18, wherein: the first DDC component comprises a firstdata receiver and a first data transmitter, which respectively receivesthe at least one first pairing parameter and transmits the received atleast one first pairing parameter to the second DDC component; and thesecond DDC component comprises a second data receiver that receives theat least one first pairing parameter from the first DDC component and asecond data transmitter that transmits the at least one first pairingparameter to the second user device from the second DDC component. 20.The method of claim 19, wherein: the first data receiver is one of aradio frequency identifier (RFID) receiver and a near fieldcommunication (NFC) receiver; and the second data transmitter is one ofa radio frequency identifier (RFID) transmitter and a near fieldcommunication (NFC) transmitter.
 21. The method of claim 12, furthercomprising: the D2D pairing assembly detecting one of (i) a physicalplacement of the first user device on the first DDC area and (ii) thefirst user device coming into proximity of and/or within communicationrange of the first DDC area; and in response to the detecting,triggering the DDC component to establish a communication with the firstuser device via a short-range wireless communication protocol supportedby the first user device.